

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Use the Debugger [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Debugger,Debugger Using,Debugger Start,Debugger Stop">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Use the Debugger</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="system_requirements.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="the_debug_window.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_BodyText"><span class="f_BodyText">The debugging components of Enterprise Architect comprise the </span><span class="f_UIControl"><a href="the_debug_window.htm">Debug</a> </span><span class="f_BodyText">window and a series of subordinate debugger windows, which you can display either from the </span><span class="f_UIControl">Debug</span><span class="f_BodyText"> window or separately using the </span><span class="f_MenuKeyField">View | Debug &amp; Profile</span><span class="f_BodyText"> menu option. You can then <a href="dockingwindows.htm">dock and combine</a> the windows to suit your working requirements.</span></p>
<p class="p_BodyText"><span class="f_BodyText">You use the debugger windows in conjunction with the <a href="thesourcecodeviewer.htm">Source Code viewer</a>, in which the code being debugged is displayed.</span></p>
<p class="p_BodyText"><span class="f_BodyText">To display the </span><span class="f_UIControl">Debug</span><span class="f_BodyText"> window, either press </span><span class="f_MenuKeyField">[Alt]+[8] </span><span class="f_BodyText">or select the </span><span class="f_MenuKeyField">View | Debug &amp; Profile | Debugger </span><span class="f_BodyText">menu option.</span></p>
<p class="p_TextIndentedL2"><img src="debug_debugger.png" width="306" height="319" border="0" alt="Debug_Debugger"></p>
<p class="p_BodyText"><span class="f_BodyText">The second toolbar icon (the blue arrow) is the </span><span class="f_MenuKeyField">Run</span><span class="f_BodyText"> debugger button; if at least one script has been configured for the currently selected package (as identified in the </span><span class="f_BodyText" style="font-style: italic;">Scripts</span><span class="f_BodyText"> folder), this</span><span class="f_MenuKeyField"> </span><span class="f_BodyText">button is enabled. If a script has not been created or is incomplete, all buttons are disabled and debugging remains unavailable.</span></p>
<p class="p_BodyText"><span class="f_BodyText">As <a href="build_scripts.htm">Build Scripts</a> are linked to a package, selecting another package in the </span><span class="f_UIControl">Project Browser</span><span class="f_BodyText"> also changes the active Build Script and, naturally, the target to be debugged.</span></p>
<p class="p_BodyText"><span class="f_BodyText">Breakpoints are recorded against the package also, and these update depending on which package is selected. You should <a href="breakpoints.htm">set and enable breakpoints</a> before starting the debugger.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Start The Debugger</span></p>
<p class="p_BodyText"><span class="f_BodyText">To start debugging click on the </span><span class="f_MenuKeyField">Run</span><span class="f_BodyText"> button or press </span><span class="f_MenuKeyField">[F6]</span><span class="f_BodyText">.</span></p>
<p class="p_BodyText"><span class="f_BodyText">The figure below shows the </span><span class="f_UIControl">Source Code</span><span class="f_BodyText"> window for a .NET application written in C#, where the debugger has been invoked.</span></p>
<p class="p_TextIndentedL2"><img src="debug_using_formcs.png" width="698" height="474" border="0" alt="Debug_Using_FormCS"></p>
<p class="p_BodyText"><span class="f_BodyText">The blue arrow and pink highlight indicate the line of execution, halted at a breakpoint.</span></p>
<p class="p_BodyText"><span class="f_BodyText">When the debugger is at a breakpoint the other information is presented in the various windows related to the </span><span class="f_UIControl">Debug </span><span class="f_BodyText">window. For example, t</span>he <a href="stack.htm">Stack window</a> displays the stack frames for any thread at a breakpoint, and the <a href="local_variables.htm">Locals window</a> displays any variables within the scope of the thread's current stack frame.</p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Stop the Debugger</span></p>
<p class="p_BodyText"><span class="f_BodyText">To stop debugging click on the</span><span class="f_MenuKeyField"> Stop</span><span class="f_BodyText"> button <img src="debug_stop.png" width="20" height="20" border="0" alt="Debug_Stop"> in the </span><span class="f_UIControl">Debug</span><span class="f_BodyText"> window toolbar, or press </span><span class="f_MenuKeyField">[Ctrl]+[Alt]+[F6]</span><span class="f_BodyText">.</span></p>
<div style="text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 5px 0px 5px 13px;"><table cellspacing="0" cellpadding="2" border="0" style="border: none; border-spacing:0px;">
<tr style="text-align:left;vertical-align:bottom;">
<td valign="bottom" width="952" bgcolor="#efeff7" style="width:952px; background-color:#efeff7;"><p class="p_TiporNote" style="border-top: none; border-right: none; border-left: none;"><span class="f_TiporNote">Notes:</span></p>
</td>
</tr>
<tr style="text-align:left;">
<td width="952" bgcolor="#f7f7ff" style="width:952px; background-color:#f7f7ff;"><p class="p_TiporNoteText"><span class="f_TiporNoteText">In most situations, the debugger ends:</span></p>
<ul style="text-indent: 0px; margin-left: 14px; list-style-position: outside;">
<li><span class="f_TiporNoteText">when it encounters breakpoints (which should be set beforehand)</span></li>
<li><span class="f_TiporNoteText">when the debug process terminates or </span></li>
<li><span class="f_TiporNoteText">when the Java Class thread exits. </span></li>
</ul>
<p class="p_TiporNoteText"><span class="f_TiporNoteText">However, due to the nature of the Java Virtual Machine, it is necessary at times for Java developers to stop the debugger manually with the </span><span class="f_MenuKeyField">Stop</span><span class="f_TiporNoteText"> button.</span></p>
</td>
</tr>
</table>
</div>




            </div>
          </div>
        </div>



</div>


</body>
</html>
